Skip to content

Clarify exemptions can apply to some conforming content#2906

Merged
mattgarrish merged 3 commits intomainfrom
editorial/issue-2849
Feb 4, 2026
Merged

Clarify exemptions can apply to some conforming content#2906
mattgarrish merged 3 commits intomainfrom
editorial/issue-2849

Conversation

@mattgarrish
Copy link
Member

The primary fix in this pull request is to reword the first paragraph and note in section 2 so that we aren't inferring that all content that needs an exemption fails accessibility standards. A Level A-conformant publication would need an EAA exemption, for example.

I also got rid of "epub creator" from the document. There weren't many instances, but the one notable change I made was to put a caution before the EAA value definitions to seek legal advice when unsure if they apply. I don't think we need to have a paragraph in every description saying it's the epub creator's responsibility to check.

Fixes #2849


Preview | Diff

Copy link
Contributor

@sueneu sueneu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I added suggestions for further simplifying lines 120, 121, 122

@mattgarrish
Copy link
Member Author

I made some different edits to the note to slim it down, and also put the fact that conforming content can claim exemptions first since it's more important than the stuff about "none" (which I'm not sure we should be saying is best practice here when we don't call that out in the accessibility spec).

If you want to make suggestions to a full paragraph, the best way is to either copy the text and edit it in your comment or, better, use github's suggestion feature. You just have to drag the + sign down to cover all the lines you want to amend and then click the suggestion button. Github will make a diff of whatever you change the suggested text to, plus it can be committed directly. I'll copy a screenshot of what I mean below.

(It's sometimes hard to be sure what people want changed when addressing single lines at a time. The first edit, for example didn't seem to follow into the next line, and the last suggestion appeared to be the same text that was there.)

suggestion

@sueneu
Copy link
Contributor

sueneu commented Feb 2, 2026

Matt, thank you!

It would be much easier to comment on the whole paragraph. Sometimes I have that option and sometimes I don’t. I’ll try working in another browser to see if I get more consistent options.

@iherman iherman added the Spec-AccessibilityExemption The issue affects the a11y:exemption property WG Note label Feb 3, 2026
@mattgarrish mattgarrish merged commit 9c8617b into main Feb 4, 2026
2 checks passed
@mattgarrish mattgarrish deleted the editorial/issue-2849 branch February 4, 2026 14:00
@github-project-automation github-project-automation bot moved this from In review to Done in PM/EPUB issues Feb 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Spec-AccessibilityExemption The issue affects the a11y:exemption property WG Note

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

Clarify that not all exempt content fails conformance

5 participants

Comments